refactor: bump style-dictionary and @tokens-studio/sd-transforms to latest#11655
Merged
refactor: bump style-dictionary and @tokens-studio/sd-transforms to latest#11655
style-dictionary and @tokens-studio/sd-transforms to latest#11655Conversation
added 30 commits
December 13, 2024 14:36
This reverts commit caed514.
this is a non-breaking change
…nd no longer match the output CSS variable
Member
Author
|
I addressed the diffs mentioned above. There are some minor differences still, but these include:
I've updated the diff links for a closer check. |
benelan
approved these changes
Mar 29, 2025
Contributor
benelan
left a comment
There was a problem hiding this comment.
Nice! Code LGTM, nothing jumped out at me besides one nitpick
benelan
added a commit
that referenced
this pull request
Mar 31, 2025
…igration-ssr * origin/dev: (23 commits) build(deps): drop @types/jsdom (#11830) build(deps): update arcgis to ^4.32.13 (#11832) build(deps): update dependency @tokens-studio/sd-transforms to v1.2.12 (#11833) docs: update list of contributors (#11829) build(deps): update dependency @types/estree to v1.0.7 (#11815) refactor: bump `style-dictionary` and `@tokens-studio/sd-transforms` to latest (#11655) chore: include all node_modules dirs in clean script (#11822) chore: ignore iml files (#11828) chore: release next build(deps): update nx monorepo to v20.6.4 (#11819) build(deps): update dependency vite to v5.4.15 (#11818) build(deps): update dependency @prettier/sync to v0.5.5 (#11814) feat(input-message): add component tokens and deprecate --calcite-input-message-spacing-value (#11759) fix: update tags (#11808) chore: cherry pick release commit from main (#11813) chore: release next build(deps): update package-lock (#11810) feat(flow-item): expose `FlowItemLike` type (#11791) revert(fab): add component tokens (#11805) docs(combobox, combobox-item): update token descriptions (#11806) ...
5 tasks
matgalla
added a commit
that referenced
this pull request
Apr 9, 2025
**Related Issue:** #11391 ## Summary Since #11655 allows us to build the final variables with the base token info, we don't need the excess token metadata. This PR removes all the fields within `attributes` from core and semantic tokens aside from the `category` field, which we will keep to assist with niche token instances and documentation purposes. ## Criteria for completion - [x] Remove `attributes` (except for `category`) from all semantic and core tokens - [x] Ensure that organization and token values are retained - [x] Ensure that the token build process is unaffected ## Previous steps - [x] #11852 ## Next steps - Add missing core color tokens - Fix incorrect core color values - Audit the structural differences between tokens and Figma variables - Restructure tokens to align with Figma variables where necessary - Address #10050 - Address #11565 - Address #11581 - Address #11725 - Address #11903 - Audit the value differences between tokens and Figma variables (mainly for percentages and typography) - Finalize token and Figma variable values with Calcite designers and developers - Update token values to align with Figma variables where necessary - Document the new token creation and modification process --------- Co-authored-by: JC Franco <jfranco@esri.com>
6 tasks
matgalla
added a commit
that referenced
this pull request
Apr 11, 2025
…11924) **Related Issue:** #11581 ## Summary Adds `low-saturation` colors that are missing when compared to the original [Calcite Colors](https://github.com/Esri/calcite-colors) repo:  Adds `medium-saturation` colors that are missing when compared to the original [Calcite Colors](https://github.com/Esri/calcite-colors) repo:  Fixes incorrect value for `--calcite-color-vibrant-blue-v-bb-180`:  Fixes incorrect value for `--calcite-color-dark-green-d-gg-430`:  NOTE: In this PR, Tokens Studio changed some minor formatting for all otherwise unchanged token JSON files. This is due to Tokens Studio bypassing the linting process. Addressed in @jcfranco's recent PR here: #11918 This PR is a part of a series of updates that address token-related issues and set them up for use with Tokens Studio. ## Criteria for completion - [x] change `--calcite-color-vibrant-blue-v-bb-180` token value to #0089DE - [x] change `--calcite-color-dark-green-d-gg-430` token value to #11AD1D - [x] add all `low-saturation` color tokens - [x] add all `medium-saturation` color tokens ## Previous steps - [x] #11655 - [x] #11852 ## Next steps - Audit the structural differences between tokens and Figma variables - Restructure tokens to align with Figma variables where necessary - Address #10050 - Address #11565 - Address #11725 - Address #11903 - Audit the value differences between tokens and Figma variables (mainly for percentages and typography) - Finalize token and Figma variable values with Calcite designers and developers - Update token values to align with Figma variables where necessary - Document the new token creation and modification process --------- Co-authored-by: JC Franco <jfranco@esri.com>
benelan
pushed a commit
that referenced
this pull request
May 14, 2025
benelan
pushed a commit
that referenced
this pull request
May 14, 2025
**Related Issue:** #11391 ## Summary Since #11655 allows us to build the final variables with the base token info, we don't need the excess token metadata. This PR removes all the fields within `attributes` from core and semantic tokens aside from the `category` field, which we will keep to assist with niche token instances and documentation purposes. ## Criteria for completion - [x] Remove `attributes` (except for `category`) from all semantic and core tokens - [x] Ensure that organization and token values are retained - [x] Ensure that the token build process is unaffected ## Previous steps - [x] #11852 ## Next steps - Add missing core color tokens - Fix incorrect core color values - Audit the structural differences between tokens and Figma variables - Restructure tokens to align with Figma variables where necessary - Address #10050 - Address #11565 - Address #11581 - Address #11725 - Address #11903 - Audit the value differences between tokens and Figma variables (mainly for percentages and typography) - Finalize token and Figma variable values with Calcite designers and developers - Update token values to align with Figma variables where necessary - Document the new token creation and modification process --------- Co-authored-by: JC Franco <jfranco@esri.com>
benelan
pushed a commit
that referenced
this pull request
May 14, 2025
…11924) **Related Issue:** #11581 ## Summary Adds `low-saturation` colors that are missing when compared to the original [Calcite Colors](https://github.com/Esri/calcite-colors) repo:  Adds `medium-saturation` colors that are missing when compared to the original [Calcite Colors](https://github.com/Esri/calcite-colors) repo:  Fixes incorrect value for `--calcite-color-vibrant-blue-v-bb-180`:  Fixes incorrect value for `--calcite-color-dark-green-d-gg-430`:  NOTE: In this PR, Tokens Studio changed some minor formatting for all otherwise unchanged token JSON files. This is due to Tokens Studio bypassing the linting process. Addressed in @jcfranco's recent PR here: #11918 This PR is a part of a series of updates that address token-related issues and set them up for use with Tokens Studio. ## Criteria for completion - [x] change `--calcite-color-vibrant-blue-v-bb-180` token value to #0089DE - [x] change `--calcite-color-dark-green-d-gg-430` token value to #11AD1D - [x] add all `low-saturation` color tokens - [x] add all `medium-saturation` color tokens ## Previous steps - [x] #11655 - [x] #11852 ## Next steps - Audit the structural differences between tokens and Figma variables - Restructure tokens to align with Figma variables where necessary - Address #10050 - Address #11565 - Address #11725 - Address #11903 - Audit the value differences between tokens and Figma variables (mainly for percentages and typography) - Finalize token and Figma variable values with Calcite designers and developers - Update token values to align with Figma variables where necessary - Document the new token creation and modification process --------- Co-authored-by: JC Franco <jfranco@esri.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related Issue: #11391
Summary
This updates the design tokens build with significant restructuring changes, based on @alisonailea’s astump/style-dictionary-4.x branch. The output remains in sync with production as much as possible to prevent breaking changes.
This is the first step required before addressing additional changes proposed in #11391.
Notable changes
Source restructuring
style-dictionary+@tokens-studio/sd-transformsconfigurationTest and snapshot updates
Transform and token updates
@cspelldictionary{semantic.color.foreground.1}source vs type)Test failures
There are a couple of expected spec test failures related to shadows:
--calcite-shadow-0: 0 0 0 0 rgba(var(--calcite-color-neutral-blk-240), 0);– the color part is invalid syntaxPrep for upcoming changes
tsconfig.jsonto support next features used in buildNext steps
Coordinate with @matgalla to update build to accommodate design token updates related to #11391.